Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

[VMC on AWS] vCenter connectivity issue due to VPN configurations. (79230)

Last Updated: 10/19/2023Categories: Best PracticesTotal Views: 265Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The on-Premises is connected to the SDDC via a Policy based VPN and the SDDC is connected to the Transit Gateway via a Route-based VPN. When a new default route is created in VMC, the VDI session in the on-Prem Data center loses access to vCenter within VMC that traverses through a policy-based VPN.

Cause

Whenever a default route is created, all traffic starts moving through the default route. This is the reason why the on-Prem Datacenter is losing connectivity to the vCenter.

Impact / Risks

The default route will not always override the VPN routes. However, there is a need for internet traffic to traverse through the route-based VPN to Transit Gateway.

Resolution

When a new default route is added to the AWS Transit Gateway and if the on-premises will try to reach cloud vCenter through the policy-based VPN, the traffic gets dropped and there will be a routing issue in the NSX T0 router. This is expected behavior.

1. Check for the reply from the VDI machine if it is reaching cloud vCenter by performing a ping test.
2. Check with on-premises networking for reverse tracert.

3. List down the tracert output of the existing configuration (without the Transit Gateway default route).

4. Cross verify if there is a routing issue in the NSX T0 router when the default route is being advertised.
5. Have the Transit Gateway re-added in with the default route and re-attempt the tracert from cloud vCenter to test the machine in order to get a better understanding of the routing path.

The alternative (preferred) solution, would be to migrate the policy-based VPN to a route-based VPN.

In case the Direct Connect (DX) is available, the DX can be used as the primary route that will propagate the Border Gateway Protocol (BGP) routes when the default route is added through the AWS Transit Gateway, and as a backup, the route-based VPN can take precedence in populating the BGP routes if DX were to have any connectivity issues. This is when the "Use VPN as a backup to Direct Connect" slider in VMC UI is selected and switched to "Enabled", and on-premises VDI workloads will still be able to route to cloud vCenter through the AWS Transit Gateway with the default route added.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Intelligence 2020/05/20 リリースのお知らせ (79158)

KB
•
Workspace ONE Intelligence for Consumer Apps 2020/05/20 リリースのお知らせ (79157)

KB
•
Workspace ONE Notebook 1.4 for iOS リリースのお知らせ (79155)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud on AWS

Related Versions:

Take Our Survey

Support Assistant